Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(platform)!: max field size and some clean up of versioning #1970

Merged
merged 2 commits into from
Jul 17, 2024

Conversation

QuantumExplorer
Copy link
Member

Issue being fixed or feature implemented

We had previously said that we would limit the field sizes on Platform. This PR achieves that with a max field size of 5 KiB (5120 bytes).

What was done?

Added a max field size.
Cleaned up some parts of versioning.

How Has This Been Tested?

Tests continue to pass

Breaking Changes

The max field size is a breaking change.

Checklist:

  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have added or updated relevant unit/integration/functional/e2e tests
  • I have added "!" to the title and described breaking changes in the corresponding section if my code contains any
  • I have made corresponding changes to the documentation if needed

For repository code-owners and collaborators only

  • I have assigned this pull request to a milestone

@QuantumExplorer QuantumExplorer requested a review from shumkov as a code owner July 17, 2024 06:03
shumkov
shumkov previously approved these changes Jul 17, 2024
Copy link
Member

@shumkov shumkov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@QuantumExplorer QuantumExplorer merged commit 785dd6c into v1.0-dev Jul 17, 2024
119 checks passed
@QuantumExplorer QuantumExplorer deleted the feat/MaxFieldSize branch July 17, 2024 08:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants